feat: update Burning Man 2026 firmware to 2.8.0.6fd990c - #411
Conversation
Published by the event/burningmesh2026 CI run to meshtastic.github.io/event/burningmesh2026/firmware-2.8.0.6fd990c/. Head commit is the opaque-relay dedup fix (#11522), which prevents an undecryptable-frame broadcast storm on the event mesh. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
Included review availability: Your plan includes up to 2 reviews per rolling hour; 1 remains after this review. 📝 WalkthroughWalkthroughThe Burning Man firmware metadata now uses release ChangesFirmware metadata
Estimated code review effort: 1 (Trivial) | ~2 minutes Merge Risk: ⚪ Minimal · up to This updates the Burning Man 2026 firmware build reference while preserving the existing event metadata shape; no actionable merge-blocking risk remains beyond normal checks and review. Suggested reviewers: Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Points the Burning Man 2026 edition at the newest
event/burningmesh2026build.Built by CI run 31985534118 from
event/burningmesh2026@6fd990c, whose head commit isfix(mesh): dedup opaque relays to prevent an undecryptable-frame broadcast storm(meshtastic/firmware#11522) — worth having on a mesh the size of Black Rock City.slug,zipUrl,releaseNotes, andgeneratedAtare unchanged — same 3-line shape as the previous two bumps.Verification
Every URL the flasher resolves for this build returns 200 at
event/burningmesh2026/firmware-2.8.0.6fd990c/:release_notes.md,firmware-2.8.0.6fd990c.json, and the per-target.mt.jsonfiles.Spot-checked
firmware-tlora-t3s3-epaper-2.8.0.6fd990c.mt.json— the board that boot-looped at DEF CON — and it carriesmt-esp32s3-ota.binatapp1withspiffsat0x340000, which is what the manifest-driven path added in #395 reads. So this build flashes with the right filenames and offsets rather than falling through to the legacy convention-based path.Event tests pass (32/32 across
firmwareUrl,eventManifest,eventDevices,firmwareStore.eventMode).Paired with the matching change in meshtastic/api, which is the source of truth this snapshot syncs from.
🤖 Generated with Claude Code
Summary by CodeRabbit
2.8.0.6fd990c.